Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Better Mumble Channel Mapping #418

Merged
merged 1 commit into from
Jun 2, 2023
Merged

Better Mumble Channel Mapping #418

merged 1 commit into from
Jun 2, 2023

Conversation

1A3Dev
Copy link
Contributor

@1A3Dev 1A3Dev commented May 29, 2023

This fixes an issue where if you have an external mumble server (not FXServer) and server IDs go over the max amount of channels that exist, it results in subsequent connections not being assigned a channel.

TDLR of this change is that each player is now assigned to whatever the first free mumble channel is instead of their server id, the current max for the free channel loop is GetConvarInt('sv_maxclients', 32) + 10 for a bit of leniency.

@AvarianKnight
Copy link
Owner

Can I know what server you're using for this? I'm a bit hesitant to merge this chain as (imo) external servers (that are not FXServer) are kind of a non-priority as they have incompatibilities with listening channels and other things so certain things that pma-voice rely on would inherently not work on those servers

@1A3Dev
Copy link
Contributor Author

1A3Dev commented May 31, 2023

Can I know what server you're using for this?

I'm using pma-voice on a FiveM server with an external Murmur server.

external servers (that are not FXServer) are kind of a non-priority

I'm aware of this and am looking into trying out an FXServer to see if it performs any better however I thought I'd do this PR to fix the issue for anyone else that is/decides to use a non-fxserver external server.

they have incompatibilities with listening channels

Murmur server v1.4.230 and above support listening channels and I've had no issues with them not working.

@AvarianKnight
Copy link
Owner

👍 I'll go ahead and merge this, if theres any reported I'm going to back it out and you can fix and make another PR

@AvarianKnight AvarianKnight merged commit 1fa272f into AvarianKnight:main Jun 2, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants